Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65179b4283b7954e3e9a465177070ba2cf80a92aaea228103f532305941ed37a

Tx prefix hash: 75865d3433a7be318041b0fbdfb014f2ff0e9f3892f026f4070748131fcc58cd
Tx public key: 60605d3ca48cb1ce1d069619b9e718c345ad0890d8dfb8cee1d4c8ae6225f3ef
Timestamp: 1722521542 Timestamp [UCT]: 2024-08-01 14:12:22 Age [y:d:h:m:s]: 00:232:15:39:01
Block: 1078457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166170 RingCT/type: yes/0
Extra: 0160605d3ca48cb1ce1d069619b9e718c345ad0890d8dfb8cee1d4c8ae6225f3ef02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f39eea8c08c3b1acfe57656b9df72af13c3a0688f189431ac2ee1440bf459dd4 0.600000000000 1551034 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": 1078467, "vin": [ { "gen": { "height": 1078457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f39eea8c08c3b1acfe57656b9df72af13c3a0688f189431ac2ee1440bf459dd4" } } ], "extra": [ 1, 96, 96, 93, 60, 164, 140, 177, 206, 29, 6, 150, 25, 185, 231, 24, 195, 69, 173, 8, 144, 216, 223, 184, 206, 225, 212, 200, 174, 98, 37, 243, 239, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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