Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5a4053a31c2782fa1bd8902a4933121217c7c814258c655df2f81f4705e6e394

Tx prefix hash: 93934c6664001e5b8f4b308032669452abf09ba561acfd833c5479e4d920b3ee
Tx public key: f08448c1a9a85c85d497c9fc13556361e3fc7681ad16deeb31d4e95b652224c4
Timestamp: 1712467877 Timestamp [UCT]: 2024-04-07 05:31:17 Age [y:d:h:m:s]: 01:009:05:41:32
Block: 995074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267597 RingCT/type: yes/0
Extra: 01f08448c1a9a85c85d497c9fc13556361e3fc7681ad16deeb31d4e95b652224c40211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 513748c7b9617b5389f7d54d2104b9ca0f77ed183e7248abf4e73d5bdd26e5f5 0.600000000000 1455478 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 995084, "vin": [ { "gen": { "height": 995074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "513748c7b9617b5389f7d54d2104b9ca0f77ed183e7248abf4e73d5bdd26e5f5" } } ], "extra": [ 1, 240, 132, 72, 193, 169, 168, 92, 133, 212, 151, 201, 252, 19, 85, 99, 97, 227, 252, 118, 129, 173, 22, 222, 235, 49, 212, 233, 91, 101, 34, 36, 196, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8