Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5915ba4ed6a8d4e55d08a169aaf697a060dbfdd1bc3a5814418b3efa978f6cb

Tx prefix hash: ceaeb4e0525978b84e15e4498cd47be3b5e72a49158bad061131a7d8b1988264
Tx public key: e51718c0de7ec2b5992486cbf51964eceedb9d11c11fc68d6f0ff6cbab057e6b
Timestamp: 1719184822 Timestamp [UCT]: 2024-06-23 23:20:22 Age [y:d:h:m:s]: 00:286:22:28:01
Block: 1050791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205026 RingCT/type: yes/0
Extra: 01e51718c0de7ec2b5992486cbf51964eceedb9d11c11fc68d6f0ff6cbab057e6b0211000000020fbbc4c5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd95b6125cbd383547924349a00d78f6fd55b501b263c02ad4f8970aeb2d5a2b 0.600000000000 1520966 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": 1050801, "vin": [ { "gen": { "height": 1050791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd95b6125cbd383547924349a00d78f6fd55b501b263c02ad4f8970aeb2d5a2b" } } ], "extra": [ 1, 229, 23, 24, 192, 222, 126, 194, 181, 153, 36, 134, 203, 245, 25, 100, 236, 238, 219, 157, 17, 193, 31, 198, 141, 111, 15, 246, 203, 171, 5, 126, 107, 2, 17, 0, 0, 0, 2, 15, 187, 196, 197, 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