Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70b5ff5e5b64302a851935dd2de615ff327541e2f24a06c5d23fadf693170189

Tx prefix hash: 786fcc8399c0c543c610a1113446d71713e2b44fed5603b2f82cb60e3bdffff9
Tx public key: 1951f93dc1dba27de3c11e88f63ee8e22fa745ea7f87c03259d0e42ce81615e9
Timestamp: 1703029444 Timestamp [UCT]: 2023-12-19 23:44:04 Age [y:d:h:m:s]: 00:276:23:01:07
Block: 916866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198384 RingCT/type: yes/0
Extra: 011951f93dc1dba27de3c11e88f63ee8e22fa745ea7f87c03259d0e42ce81615e902110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 315a403be91842037b83263d2c04727551decde6d71df32e7c0d991994590d6d 0.600000000000 1374428 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": 916876, "vin": [ { "gen": { "height": 916866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "315a403be91842037b83263d2c04727551decde6d71df32e7c0d991994590d6d" } } ], "extra": [ 1, 25, 81, 249, 61, 193, 219, 162, 125, 227, 193, 30, 136, 246, 62, 232, 226, 47, 167, 69, 234, 127, 135, 192, 50, 89, 208, 228, 44, 232, 22, 21, 233, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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