Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64b9ec380c8c4a75685230750abda3a74bc3b938d58a975a13b039677b31b1ba

Tx prefix hash: 3af65ed6fd53e1b014e62c171ed7ab6d7f07fd9d234df153063cfb8710d9f1ed
Tx public key: 403f4bd276e568616fa6bcd708fa340748cc44facf005e13459f095ac2a184b3
Timestamp: 1723712093 Timestamp [UCT]: 2024-08-15 08:54:53 Age [y:d:h:m:s]: 00:234:04:39:15
Block: 1088336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167236 RingCT/type: yes/0
Extra: 01403f4bd276e568616fa6bcd708fa340748cc44facf005e13459f095ac2a184b3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808d4c63b71ac2ea998f0ab67f442a015f1043d6c056b050c3fb435df94ba528 0.600000000000 1562951 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": 1088346, "vin": [ { "gen": { "height": 1088336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808d4c63b71ac2ea998f0ab67f442a015f1043d6c056b050c3fb435df94ba528" } } ], "extra": [ 1, 64, 63, 75, 210, 118, 229, 104, 97, 111, 166, 188, 215, 8, 250, 52, 7, 72, 204, 68, 250, 207, 0, 94, 19, 69, 159, 9, 90, 194, 161, 132, 179, 2, 17, 0, 0, 0, 4, 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