Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a0d5c1230055162cf4e06373953056880b13e18eef0b5f30c991a79e98cf474

Tx prefix hash: 85b4b048a25a06a918061b02359ce0123d09a32c3926d1c5b905cc7c807593b6
Tx public key: d59699df8cf25ca2a0e003c521eaa204287278cfa5ec330df10a3cf8fb47aee9
Timestamp: 1709765167 Timestamp [UCT]: 2024-03-06 22:46:07 Age [y:d:h:m:s]: 00:262:19:16:53
Block: 972713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188137 RingCT/type: yes/0
Extra: 01d59699df8cf25ca2a0e003c521eaa204287278cfa5ec330df10a3cf8fb47aee902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b726ed074e57e6e032ec83ea4432e9912b6ce7a48ccf666533d86539516cf5fe 0.600000000000 1432632 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": 972723, "vin": [ { "gen": { "height": 972713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b726ed074e57e6e032ec83ea4432e9912b6ce7a48ccf666533d86539516cf5fe" } } ], "extra": [ 1, 213, 150, 153, 223, 140, 242, 92, 162, 160, 224, 3, 197, 33, 234, 162, 4, 40, 114, 120, 207, 165, 236, 51, 13, 241, 10, 60, 248, 251, 71, 174, 233, 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