Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e37083dcff3b806e29e71478e8966e0d94d0d5e731f31413264c97522e11857

Tx prefix hash: 8a02d42b883003008a4a83f216d0666108dd79e841a75d9008b0ca36633a3b34
Tx public key: 57335a47ecbbead70c590d928ec21672fe592bd6b32f5b44ec49f73bbfb20f69
Timestamp: 1577053604 Timestamp [UCT]: 2019-12-22 22:26:44 Age [y:d:h:m:s]: 04:342:06:02:30
Block: 29760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133551 RingCT/type: yes/0
Extra: 0157335a47ecbbead70c590d928ec21672fe592bd6b32f5b44ec49f73bbfb20f690211000000049159db1e000000000000000000

1 output(s) for total of 489.095456786000 dcy

stealth address amount amount idx
00: f3e405fba2a13d24cf2d1c85eff863d456064fd32d88bd4e425ca58e38d1d7e4 489.095456786000 49026 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": 29770, "vin": [ { "gen": { "height": 29760 } } ], "vout": [ { "amount": 489095456786, "target": { "key": "f3e405fba2a13d24cf2d1c85eff863d456064fd32d88bd4e425ca58e38d1d7e4" } } ], "extra": [ 1, 87, 51, 90, 71, 236, 187, 234, 215, 12, 89, 13, 146, 142, 194, 22, 114, 254, 89, 43, 214, 179, 47, 91, 68, 236, 73, 247, 59, 191, 178, 15, 105, 2, 17, 0, 0, 0, 4, 145, 89, 219, 30, 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