Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4aa5d243d3888cc0c61dbfcd7768526b332b82eaa23562ed00947e66f7b1be

Tx prefix hash: ec302770ccd04332ee215b4c7e024476ace6d51177d023047e43ad3fc9042d20
Tx public key: 1bf82ba6a64ff0b2f5644e9e03b18f10bbebfa7020c8d5e9a54c33a0dcf673e9
Timestamp: 1719706806 Timestamp [UCT]: 2024-06-30 00:20:06 Age [y:d:h:m:s]: 00:271:20:15:31
Block: 1055112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194247 RingCT/type: yes/0
Extra: 011bf82ba6a64ff0b2f5644e9e03b18f10bbebfa7020c8d5e9a54c33a0dcf673e902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cf9c08e2dac4789c9c2cf6ec5827ac86f46c3d1673b588787789524a6924a69 0.600000000000 1525505 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": 1055122, "vin": [ { "gen": { "height": 1055112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cf9c08e2dac4789c9c2cf6ec5827ac86f46c3d1673b588787789524a6924a69" } } ], "extra": [ 1, 27, 248, 43, 166, 166, 79, 240, 178, 245, 100, 78, 158, 3, 177, 143, 16, 187, 235, 250, 112, 32, 200, 213, 233, 165, 76, 51, 160, 220, 246, 115, 233, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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