Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b17487abf383b1ac44bf66d263f2adda43a436e9aba97fc3d9c0831846a02eae

Tx prefix hash: 2245d11b2d493a27d0079bf45d876a2aad3e204aa7b76c1a492ae17208d42f1c
Tx public key: 3c61e901203e3fad97ca7c790e905386e585ef852c025e3dbdfba516cc91fc5b
Timestamp: 1730482028 Timestamp [UCT]: 2024-11-01 17:27:08 Age [y:d:h:m:s]: 00:082:05:52:44
Block: 1144375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58796 RingCT/type: yes/0
Extra: 013c61e901203e3fad97ca7c790e905386e585ef852c025e3dbdfba516cc91fc5b021100000003007f978a000000000000000000

1 output(s) for total of 0.607990000000 dcy

stealth address amount amount idx
00: e2a42e9e64ad71596b0ce5fce7f4bc3090e5aef1d8b84625cbaa2dac3b91f0b6 0.607990000000 1628572 of 0

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": 1144385, "vin": [ { "gen": { "height": 1144375 } } ], "vout": [ { "amount": 607990000, "target": { "key": "e2a42e9e64ad71596b0ce5fce7f4bc3090e5aef1d8b84625cbaa2dac3b91f0b6" } } ], "extra": [ 1, 60, 97, 233, 1, 32, 62, 63, 173, 151, 202, 124, 121, 14, 144, 83, 134, 229, 133, 239, 133, 44, 2, 94, 61, 189, 251, 165, 22, 204, 145, 252, 91, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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