Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1d1b3254e1d489d566ca4db9e1f3f13c4928f91dab504f77e41892c96e98441

Tx prefix hash: bfd1fa2db18f2e2e2e981bef3f951bb6020d0c306c5061028487f68b627b9cb7
Tx public key: 627e05653183821dd9ac77865e4fd17356cb91fbdbbd21a6a374867dafb7713b
Timestamp: 1738074821 Timestamp [UCT]: 2025-01-28 14:33:41 Age [y:d:h:m:s]: 00:296:21:28:31
Block: 1207005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209929 RingCT/type: yes/0
Extra: 01627e05653183821dd9ac77865e4fd17356cb91fbdbbd21a6a374867dafb7713b021100000013621f8af3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2d733b920bfa96d11251b51c887416e3dd0485a8be0f106999a735f5bc10a97 0.600000000000 1693726 of 15

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": 1207015, "vin": [ { "gen": { "height": 1207005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2d733b920bfa96d11251b51c887416e3dd0485a8be0f106999a735f5bc10a97" } } ], "extra": [ 1, 98, 126, 5, 101, 49, 131, 130, 29, 217, 172, 119, 134, 94, 79, 209, 115, 86, 203, 145, 251, 219, 189, 33, 166, 163, 116, 134, 125, 175, 183, 113, 59, 2, 17, 0, 0, 0, 19, 98, 31, 138, 243, 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