Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57998971b46259dc5b96017dec52847ac0908527fd28053378f9215b42c88f87

Tx prefix hash: 314fa415bcb4f859a69a489c99776d05521256710f197050517debd6f980c20c
Tx public key: 758a07cec186a4c83f6f029924f098379c9b2c0441a4c08cbfad28e33f6d4ab9
Timestamp: 1730560537 Timestamp [UCT]: 2024-11-02 15:15:37 Age [y:d:h:m:s]: 00:022:03:45:25
Block: 1145015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15862 RingCT/type: yes/0
Extra: 01758a07cec186a4c83f6f029924f098379c9b2c0441a4c08cbfad28e33f6d4ab9021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b384fa64fde6882919e5c38bfe6ca0bf6ecb8df9abf68a2d31b3bb9170095f7a 0.600000000000 1629376 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": 1145025, "vin": [ { "gen": { "height": 1145015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b384fa64fde6882919e5c38bfe6ca0bf6ecb8df9abf68a2d31b3bb9170095f7a" } } ], "extra": [ 1, 117, 138, 7, 206, 193, 134, 164, 200, 63, 111, 2, 153, 36, 240, 152, 55, 156, 155, 44, 4, 65, 164, 192, 140, 191, 173, 40, 227, 63, 109, 74, 185, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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