Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbc1a8572628ca442b203cee8c2b811f5a5e1c5701fed51b689f7ff6c1b21c99

Tx prefix hash: d11af89bbc91207e21ed7fd161e4dc51e44cfd0da2b0f56cd389f9026f72993e
Tx public key: 9670566b1b85204d571e0e9ebf1227f01d63bc15abea435ba8f1ffbe6c8383f6
Timestamp: 1699445008 Timestamp [UCT]: 2023-11-08 12:03:28 Age [y:d:h:m:s]: 01:131:23:23:28
Block: 887154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355518 RingCT/type: yes/0
Extra: 019670566b1b85204d571e0e9ebf1227f01d63bc15abea435ba8f1ffbe6c8383f6021100000003faf35c9c000000000000000000

1 output(s) for total of 0.705489452000 dcy

stealth address amount amount idx
00: 485bfed4d1186a7b63451d435fd99ccaebc335902983e3808ea79924c944ebc3 0.705489452000 1343011 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": 887164, "vin": [ { "gen": { "height": 887154 } } ], "vout": [ { "amount": 705489452, "target": { "key": "485bfed4d1186a7b63451d435fd99ccaebc335902983e3808ea79924c944ebc3" } } ], "extra": [ 1, 150, 112, 86, 107, 27, 133, 32, 77, 87, 30, 14, 158, 191, 18, 39, 240, 29, 99, 188, 21, 171, 234, 67, 91, 168, 241, 255, 190, 108, 131, 131, 246, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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