Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747f10f733d863f4156b96bf86051a6e9fee4ca1fd283a8c99170660d47e07da

Tx prefix hash: 16b9041e731c09ca64462b67abc5f58c8a15e8ffd993dec38cefc71011c422d3
Tx public key: 884ef3476f570e2bb55e297b72771317307ffb632d335656b0c7a00c1a8a7e9e
Timestamp: 1736316877 Timestamp [UCT]: 2025-01-08 06:14:37 Age [y:d:h:m:s]: 00:070:16:02:15
Block: 1192694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50304 RingCT/type: yes/0
Extra: 01884ef3476f570e2bb55e297b72771317307ffb632d335656b0c7a00c1a8a7e9e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6db248b3ee07153b8989b0dc2a76ef49667dba6ba0c32436e7a742f7ea18f125 0.600000000000 1679249 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": 1192704, "vin": [ { "gen": { "height": 1192694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6db248b3ee07153b8989b0dc2a76ef49667dba6ba0c32436e7a742f7ea18f125" } } ], "extra": [ 1, 136, 78, 243, 71, 111, 87, 14, 43, 181, 94, 41, 123, 114, 119, 19, 23, 48, 127, 251, 99, 45, 51, 86, 86, 176, 199, 160, 12, 26, 138, 126, 158, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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