Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffac57540bbf21ba19756862d827de2f1e85dda4e4cde305aa700e3e3c2768eb

Tx prefix hash: b1732ed2ab520f0392724d9a2a5b5fac0b2c2f3dcbf92ddc35e1d36faab17993
Tx public key: 1fc66a0618c261a70b4c28ff76faf74f684154899dfe8ae75109caa0ea52e42f
Timestamp: 1717692462 Timestamp [UCT]: 2024-06-06 16:47:42 Age [y:d:h:m:s]: 01:155:04:46:48
Block: 1038426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369490 RingCT/type: yes/0
Extra: 011fc66a0618c261a70b4c28ff76faf74f684154899dfe8ae75109caa0ea52e42f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de9967ea329d72a06aec29252a9e747920998986372df5d64cb1208aed4d2604 0.600000000000 1506987 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": 1038436, "vin": [ { "gen": { "height": 1038426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de9967ea329d72a06aec29252a9e747920998986372df5d64cb1208aed4d2604" } } ], "extra": [ 1, 31, 198, 106, 6, 24, 194, 97, 167, 11, 76, 40, 255, 118, 250, 247, 79, 104, 65, 84, 137, 157, 254, 138, 231, 81, 9, 202, 160, 234, 82, 228, 47, 2, 17, 0, 0, 0, 2, 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