Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: febe47117385baf59a39da5256498e818deae8b437c374f668dc271e31a677b5

Tx prefix hash: 394130bf80a1336a687efc8a5809754e3f4b951fcd4a0e53d3aa2b866c246c82
Tx public key: 39151646a1db7759b3c1074aebb50c2ff64cfce1bfffaa2a2d6251d1c33b094d
Timestamp: 1638807395 Timestamp [UCT]: 2021-12-06 16:16:35 Age [y:d:h:m:s]: 03:333:15:32:48
Block: 389766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1014882 RingCT/type: yes/0
Extra: 0139151646a1db7759b3c1074aebb50c2ff64cfce1bfffaa2a2d6251d1c33b094d0211000000131cab2639000000000000000000

1 output(s) for total of 31.372115761000 dcy

stealth address amount amount idx
00: f504a0c1ee89668c6319cfc000dfcef16aaa7dc952cbd694ad1f8fbce67b9d46 31.372115761000 785125 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": 389776, "vin": [ { "gen": { "height": 389766 } } ], "vout": [ { "amount": 31372115761, "target": { "key": "f504a0c1ee89668c6319cfc000dfcef16aaa7dc952cbd694ad1f8fbce67b9d46" } } ], "extra": [ 1, 57, 21, 22, 70, 161, 219, 119, 89, 179, 193, 7, 74, 235, 181, 12, 47, 246, 76, 252, 225, 191, 255, 170, 42, 45, 98, 81, 209, 195, 59, 9, 77, 2, 17, 0, 0, 0, 19, 28, 171, 38, 57, 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