Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45a000dccd3641d62bd3c2f28ae72978ed1a393372410fe370a91387d71ce0d

Tx prefix hash: 731044e25584e4f3cce8258297a0bf54e8b2b04df7987312ed5e6a46264c78b5
Tx public key: 77303821fd9916d9a071f8ed5672368b90129b098fe425c39219da535a9e9f46
Timestamp: 1713665965 Timestamp [UCT]: 2024-04-21 02:19:25 Age [y:d:h:m:s]: 00:204:04:04:42
Block: 1005033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146168 RingCT/type: yes/0
Extra: 0177303821fd9916d9a071f8ed5672368b90129b098fe425c39219da535a9e9f460211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05e1769a00bb7a942ed0d4efe77648a1e0cf9e69857e90914aecc5c77a2e387b 0.600000000000 1465611 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": 1005043, "vin": [ { "gen": { "height": 1005033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05e1769a00bb7a942ed0d4efe77648a1e0cf9e69857e90914aecc5c77a2e387b" } } ], "extra": [ 1, 119, 48, 56, 33, 253, 153, 22, 217, 160, 113, 248, 237, 86, 114, 54, 139, 144, 18, 155, 9, 143, 228, 37, 195, 146, 25, 218, 83, 90, 158, 159, 70, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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