Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1e03b206c1a59a75d8060e138779cd861e1db15c973a6e733ce4f567dfc9048

Tx prefix hash: f0bfc0504a4c56b66277f00a32a21bada7900a4d38de7a4ae98cd38b342300ec
Tx public key: 411a5fcbfa0ea4be8097c75246620113b788febbfaf0d13fd580a6447e79f489
Timestamp: 1722470548 Timestamp [UCT]: 2024-08-01 00:02:28 Age [y:d:h:m:s]: 00:259:09:50:18
Block: 1078031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185309 RingCT/type: yes/0
Extra: 01411a5fcbfa0ea4be8097c75246620113b788febbfaf0d13fd580a6447e79f489021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b07c9147e4d8b2566cc12ccfc3b5a3c0bba7b8e8be191a26eb82146cb7daefd 0.600000000000 1550586 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": 1078041, "vin": [ { "gen": { "height": 1078031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b07c9147e4d8b2566cc12ccfc3b5a3c0bba7b8e8be191a26eb82146cb7daefd" } } ], "extra": [ 1, 65, 26, 95, 203, 250, 14, 164, 190, 128, 151, 199, 82, 70, 98, 1, 19, 183, 136, 254, 187, 250, 240, 209, 63, 213, 128, 166, 68, 126, 121, 244, 137, 2, 17, 0, 0, 0, 8, 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