Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a22f820dc27d94effeddc6a6364231b68573c074a3b71fc1a0d1a7b53c6301f4

Tx prefix hash: 41ffda5256cd32ec72d3dcb4953ff83833664ae76510a9da51c8aa0ca9fd2153
Tx public key: a8691e0edb2d9cc56a388319ba8c12befdad0f25800673a3680d489a42cf3d24
Timestamp: 1580880775 Timestamp [UCT]: 2020-02-05 05:32:55 Age [y:d:h:m:s]: 05:273:18:36:20
Block: 58713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1345694 RingCT/type: yes/0
Extra: 01a8691e0edb2d9cc56a388319ba8c12befdad0f25800673a3680d489a42cf3d2402110000000149b77a3d000000000000000000

1 output(s) for total of 392.157276962000 dcy

stealth address amount amount idx
00: 0fbb69df77d9727d4f435fdad62045650f8dfbe34054487f72ef41c3d08481c0 392.157276962000 108549 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": 58723, "vin": [ { "gen": { "height": 58713 } } ], "vout": [ { "amount": 392157276962, "target": { "key": "0fbb69df77d9727d4f435fdad62045650f8dfbe34054487f72ef41c3d08481c0" } } ], "extra": [ 1, 168, 105, 30, 14, 219, 45, 156, 197, 106, 56, 131, 25, 186, 140, 18, 190, 253, 173, 15, 37, 128, 6, 115, 163, 104, 13, 72, 154, 66, 207, 61, 36, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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