Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2462b0f2a244a1e4870563be73ec2a524502bdec4d23b8b4abc9e8881ab767b

Tx prefix hash: e48b027ec35ce8cdbec5e38d33731fe9c894f387ad562a891b446403f087b734
Tx public key: 6ba599ad1eaf47157e76e4d55ac1f4b8fad2af89e4d6bacb546a9f53c2f96604
Timestamp: 1718662412 Timestamp [UCT]: 2024-06-17 22:13:32 Age [y:d:h:m:s]: 01:142:20:12:03
Block: 1046466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360642 RingCT/type: yes/0
Extra: 016ba599ad1eaf47157e76e4d55ac1f4b8fad2af89e4d6bacb546a9f53c2f9660402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e95351235384961fbaea87b29a008cb88407bb1bbb39a10f6618168ae6e465a9 0.600000000000 1516279 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": 1046476, "vin": [ { "gen": { "height": 1046466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e95351235384961fbaea87b29a008cb88407bb1bbb39a10f6618168ae6e465a9" } } ], "extra": [ 1, 107, 165, 153, 173, 30, 175, 71, 21, 126, 118, 228, 213, 90, 193, 244, 184, 250, 210, 175, 137, 228, 214, 186, 203, 84, 106, 159, 83, 194, 249, 102, 4, 2, 17, 0, 0, 0, 4, 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