Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6de9a32aa337c4fe6034ea8e7b04b839154d95066f8eb0ed58a8288e1229b304

Tx prefix hash: e0024e70ac5e0a151b9c24e4561d7aa9576815ee549bddce4858e6348506c97f
Tx public key: 924e80b4b6b46b35f7422e3d6524b155e95420b9f840affd73d4e1779689c273
Timestamp: 1722543744 Timestamp [UCT]: 2024-08-01 20:22:24 Age [y:d:h:m:s]: 00:161:19:17:53
Block: 1078637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115766 RingCT/type: yes/0
Extra: 01924e80b4b6b46b35f7422e3d6524b155e95420b9f840affd73d4e1779689c273021100000002e914dd15000000000000000000

1 output(s) for total of 0.613580000000 dcy

stealth address amount amount idx
00: b29436265fa98cf9ef1000b48bbeb6e5f75208d2374b494f5c2d8a01c35dbbaf 0.613580000000 1551250 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": 1078647, "vin": [ { "gen": { "height": 1078637 } } ], "vout": [ { "amount": 613580000, "target": { "key": "b29436265fa98cf9ef1000b48bbeb6e5f75208d2374b494f5c2d8a01c35dbbaf" } } ], "extra": [ 1, 146, 78, 128, 180, 182, 180, 107, 53, 247, 66, 46, 61, 101, 36, 177, 85, 233, 84, 32, 185, 248, 64, 175, 253, 115, 212, 225, 119, 150, 137, 194, 115, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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