Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8236087949687736bcd1ec3f5a23efd1637ef2377b9f7731d44e50c316ceb764

Tx prefix hash: b01630b42e86399851cfca6695b385a1132e0ff0f79009405c65e5fb1e0835ea
Tx public key: d0638ce72b9fc9768e50e209dbbcefaa391df03d9985a208fd70a89e382ddc47
Timestamp: 1700928702 Timestamp [UCT]: 2023-11-25 16:11:42 Age [y:d:h:m:s]: 01:175:03:46:57
Block: 899443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386375 RingCT/type: yes/0
Extra: 01d0638ce72b9fc9768e50e209dbbcefaa391df03d9985a208fd70a89e382ddc4702110000000375e3f0e9000000000000000000

1 output(s) for total of 0.642350326000 dcy

stealth address amount amount idx
00: 0c8b24bce999ecee7ceed996d9c6a4b0e0a16a83b454ecf3cd5a98757a5dc1d5 0.642350326000 1355898 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": 899453, "vin": [ { "gen": { "height": 899443 } } ], "vout": [ { "amount": 642350326, "target": { "key": "0c8b24bce999ecee7ceed996d9c6a4b0e0a16a83b454ecf3cd5a98757a5dc1d5" } } ], "extra": [ 1, 208, 99, 140, 231, 43, 159, 201, 118, 142, 80, 226, 9, 219, 188, 239, 170, 57, 29, 240, 61, 153, 133, 162, 8, 253, 112, 168, 158, 56, 45, 220, 71, 2, 17, 0, 0, 0, 3, 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