Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aaa346d19357ee2235c58ef81dc6e5362ee2d46ab715a6d82327350f45c1458

Tx prefix hash: 639c27d3291958a0f941b544a405a54c61bbeca4106bceebe5390bb8f9cc4e4f
Tx public key: 8da0ef731bdcc20651f962f1e22a276620973d1cf7a9e5ca9670d804e912f84a
Timestamp: 1577579448 Timestamp [UCT]: 2019-12-29 00:30:48 Age [y:d:h:m:s]: 05:308:12:06:03
Block: 33932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1368001 RingCT/type: yes/0
Extra: 018da0ef731bdcc20651f962f1e22a276620973d1cf7a9e5ca9670d804e912f84a0211000000114ac5aa02000000000000000000

1 output(s) for total of 473.772724803000 dcy

stealth address amount amount idx
00: a15b8c1712a160075173167f724d4a9baab5275296d9b5d485aaa2171bc4bc6b 473.772724803000 57043 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": 33942, "vin": [ { "gen": { "height": 33932 } } ], "vout": [ { "amount": 473772724803, "target": { "key": "a15b8c1712a160075173167f724d4a9baab5275296d9b5d485aaa2171bc4bc6b" } } ], "extra": [ 1, 141, 160, 239, 115, 27, 220, 194, 6, 81, 249, 98, 241, 226, 42, 39, 102, 32, 151, 61, 28, 247, 169, 229, 202, 150, 112, 216, 4, 233, 18, 248, 74, 2, 17, 0, 0, 0, 17, 74, 197, 170, 2, 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