Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc534da72c5b8b9ae103eded3050eb362a7253130522612448e04a5bfa829516

Tx prefix hash: 4badb7f0843b64f7c3b59a067c592aa2eb39f1be72a1b5220fe5bd577fce3671
Tx public key: 7adf30239fc48f3ef025944e5feab280ed831e92183bbc2a13289a3008aa6b5d
Timestamp: 1728467390 Timestamp [UCT]: 2024-10-09 09:49:50 Age [y:d:h:m:s]: 00:197:03:26:35
Block: 1127754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140702 RingCT/type: yes/0
Extra: 017adf30239fc48f3ef025944e5feab280ed831e92183bbc2a13289a3008aa6b5d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6de9bbe397938a59667540fe0703fb557fdf1eab9ec952fcd6a10a6bbc0de3d2 0.600000000000 1610565 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": 1127764, "vin": [ { "gen": { "height": 1127754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6de9bbe397938a59667540fe0703fb557fdf1eab9ec952fcd6a10a6bbc0de3d2" } } ], "extra": [ 1, 122, 223, 48, 35, 159, 196, 143, 62, 240, 37, 148, 78, 95, 234, 178, 128, 237, 131, 30, 146, 24, 59, 188, 42, 19, 40, 154, 48, 8, 170, 107, 93, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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