Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b4f7c703b35955e28d992e4847f56b961f4afd3de282eaf3d1d511632c5d36b

Tx prefix hash: 3f4733c7bc922c8e59c5ada5486799da5e633d351f75cf9b2b7cbc530107e750
Tx public key: 82afa48b18a3d1171cd44ca27da12ad5f8f08b5c8411bc3a417b505ef1456a98
Timestamp: 1696566203 Timestamp [UCT]: 2023-10-06 04:23:23 Age [y:d:h:m:s]: 01:103:12:21:35
Block: 863476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335251 RingCT/type: yes/0
Extra: 0182afa48b18a3d1171cd44ca27da12ad5f8f08b5c8411bc3a417b505ef1456a98021100000002faf35c9c000000000000000000

1 output(s) for total of 0.845172977000 dcy

stealth address amount amount idx
00: 8a9ae4e6f4f1f73231ad7df1486896a07c0f561ec2e510694166d8a5e5b8a6c8 0.845172977000 1317932 of 0

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": 863486, "vin": [ { "gen": { "height": 863476 } } ], "vout": [ { "amount": 845172977, "target": { "key": "8a9ae4e6f4f1f73231ad7df1486896a07c0f561ec2e510694166d8a5e5b8a6c8" } } ], "extra": [ 1, 130, 175, 164, 139, 24, 163, 209, 23, 28, 212, 76, 162, 125, 161, 42, 213, 248, 240, 139, 92, 132, 17, 188, 58, 65, 123, 80, 94, 241, 69, 106, 152, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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