Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7338ef7108d697f7874d0c007d66604a37b17e4bd9448e23d81188841a745081

Tx prefix hash: 7e0356fb1e603a51a76869cc842a884eb30d91892f52d77ad55389ff234cf049
Tx public key: 3c307dc24e4a00fa6884742b05b62fdc164b0e04e9e81b917d9cd10b129502b4
Timestamp: 1726247505 Timestamp [UCT]: 2024-09-13 17:11:45 Age [y:d:h:m:s]: 00:071:16:10:50
Block: 1109349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51239 RingCT/type: yes/0
Extra: 013c307dc24e4a00fa6884742b05b62fdc164b0e04e9e81b917d9cd10b129502b4021100000007e914dd15000000000000000000

1 output(s) for total of 0.608020000000 dcy

stealth address amount amount idx
00: b0bcb7604a53b46d822ee1fb1223c547ab4ed144cc1d28f270abb5be775e75b4 0.608020000000 1587566 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": 1109359, "vin": [ { "gen": { "height": 1109349 } } ], "vout": [ { "amount": 608020000, "target": { "key": "b0bcb7604a53b46d822ee1fb1223c547ab4ed144cc1d28f270abb5be775e75b4" } } ], "extra": [ 1, 60, 48, 125, 194, 78, 74, 0, 250, 104, 132, 116, 43, 5, 182, 47, 220, 22, 75, 14, 4, 233, 232, 27, 145, 125, 156, 209, 11, 18, 149, 2, 180, 2, 17, 0, 0, 0, 7, 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