Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c8599104eda4d4a31419764bfb4fa50af33359903e66738a6d0e546d2bebb01

Tx prefix hash: fda5192787980e257baa36fd451e9fe6db69b5e0616edb4e49fae644b30e8cf2
Tx public key: cf32724cfd5f4033960ff93f0300d831142a639581d22f5a252153a6fc1a271e
Timestamp: 1699893707 Timestamp [UCT]: 2023-11-13 16:41:47 Age [y:d:h:m:s]: 01:146:02:31:03
Block: 890867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365592 RingCT/type: yes/0
Extra: 01cf32724cfd5f4033960ff93f0300d831142a639581d22f5a252153a6fc1a271e02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.685784728000 dcy

stealth address amount amount idx
00: ca3c0bc5b8389875169872a499df6c19c36a43d5be619e4c2940921c994582dd 0.685784728000 1346898 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": 890877, "vin": [ { "gen": { "height": 890867 } } ], "vout": [ { "amount": 685784728, "target": { "key": "ca3c0bc5b8389875169872a499df6c19c36a43d5be619e4c2940921c994582dd" } } ], "extra": [ 1, 207, 50, 114, 76, 253, 95, 64, 51, 150, 15, 249, 63, 3, 0, 216, 49, 20, 42, 99, 149, 129, 210, 47, 90, 37, 33, 83, 166, 252, 26, 39, 30, 2, 17, 0, 0, 0, 5, 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