Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14283698cbdd3a798ba37fe1bc101238f4a3d02c1e6ee9b48a3a3e961b99aa88

Tx prefix hash: 9bdfd70479d74aff9df6631ed214dffbbde92bd75cc43fc469522b811cb2a44e
Tx public key: 4b178c0faf209fc9f68f1b58bb01a543f70fd3578e9fbda1f86760aae443cd49
Timestamp: 1719705370 Timestamp [UCT]: 2024-06-29 23:56:10 Age [y:d:h:m:s]: 00:258:14:56:44
Block: 1055103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184812 RingCT/type: yes/0
Extra: 014b178c0faf209fc9f68f1b58bb01a543f70fd3578e9fbda1f86760aae443cd4902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7405f60d036389aa939ce44b4e6f4255f43bc9893cb35539fbcd339463082c26 0.600000000000 1525496 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": 1055113, "vin": [ { "gen": { "height": 1055103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7405f60d036389aa939ce44b4e6f4255f43bc9893cb35539fbcd339463082c26" } } ], "extra": [ 1, 75, 23, 140, 15, 175, 32, 159, 201, 246, 143, 27, 88, 187, 1, 165, 67, 247, 15, 211, 87, 142, 159, 189, 161, 248, 103, 96, 170, 228, 67, 205, 73, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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