Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bf5fd0f849ed005bddf628dfcdaa4af17751bf2f3b02446bcc1c7a4e0bc2822

Tx prefix hash: 6ae73aac12f575074d0e015da2a91f4858c3092b1e8c1630e57e0509627cc372
Tx public key: eff9ebc669e46f6d575b9f2a40369e42d86f4b6334991728d0df2a8f4d296f78
Timestamp: 1726999745 Timestamp [UCT]: 2024-09-22 10:09:05 Age [y:d:h:m:s]: 00:173:13:14:35
Block: 1115590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123855 RingCT/type: yes/0
Extra: 01eff9ebc669e46f6d575b9f2a40369e42d86f4b6334991728d0df2a8f4d296f7802110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ada7117962d74198273165973a16493e9706e8c3e24fcbdae233963f7d368ec 0.600000000000 1595775 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": 1115600, "vin": [ { "gen": { "height": 1115590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ada7117962d74198273165973a16493e9706e8c3e24fcbdae233963f7d368ec" } } ], "extra": [ 1, 239, 249, 235, 198, 105, 228, 111, 109, 87, 91, 159, 42, 64, 54, 158, 66, 216, 111, 75, 99, 52, 153, 23, 40, 208, 223, 42, 143, 77, 41, 111, 120, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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