Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 387d1274906e18f5cdef6fb789f87cc9202b1a8c3aa576494660a8f5bc1bcdb3

Tx prefix hash: 3fefff408d8c6cfd3c3d93f94c70f0f99940029dd615e63c5a06f8ee1d1ca27f
Tx public key: 300a8f04d5ecace772f16ca88e5e3449cc793818d071cae282da7017f8aaf31f
Timestamp: 1638008216 Timestamp [UCT]: 2021-11-27 10:16:56 Age [y:d:h:m:s]: 03:106:13:51:17
Block: 383187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 854846 RingCT/type: yes/0
Extra: 01300a8f04d5ecace772f16ca88e5e3449cc793818d071cae282da7017f8aaf31f02110000000df6cc1430000000000000000000

1 output(s) for total of 32.986996666000 dcy

stealth address amount amount idx
00: 6c8350fe64d5c57fd590f9b9c91184b463ec77b769357828e98ab3b08f202483 32.986996666000 773668 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": 383197, "vin": [ { "gen": { "height": 383187 } } ], "vout": [ { "amount": 32986996666, "target": { "key": "6c8350fe64d5c57fd590f9b9c91184b463ec77b769357828e98ab3b08f202483" } } ], "extra": [ 1, 48, 10, 143, 4, 213, 236, 172, 231, 114, 241, 108, 168, 142, 94, 52, 73, 204, 121, 56, 24, 208, 113, 202, 226, 130, 218, 112, 23, 248, 170, 243, 31, 2, 17, 0, 0, 0, 13, 246, 204, 20, 48, 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