Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b1957efe6ea5467cd3d4efbbbcf39b249e87e6b8a76e39f589c08c730f16456

Tx prefix hash: 204c6c6cf83477eb2836de08444f61ce11c917ee2682ed3f8dc9b540c2c5e764
Tx public key: 1c7c6cdaa81bbbe2f93a96fc9797377ddbfe63724e60b3f9e6006738efe59b7b
Timestamp: 1671863903 Timestamp [UCT]: 2022-12-24 06:38:23 Age [y:d:h:m:s]: 02:114:22:55:54
Block: 659363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 603844 RingCT/type: yes/0
Extra: 011c7c6cdaa81bbbe2f93a96fc9797377ddbfe63724e60b3f9e6006738efe59b7b0211000000027e406890000000000000000000

1 output(s) for total of 4.011036733000 dcy

stealth address amount amount idx
00: 564212a10703e57c6c36faa8991447967aa9d2fd1af1eca73b958ae1b582d61d 4.011036733000 1100064 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": 659373, "vin": [ { "gen": { "height": 659363 } } ], "vout": [ { "amount": 4011036733, "target": { "key": "564212a10703e57c6c36faa8991447967aa9d2fd1af1eca73b958ae1b582d61d" } } ], "extra": [ 1, 28, 124, 108, 218, 168, 27, 187, 226, 249, 58, 150, 252, 151, 151, 55, 125, 219, 254, 99, 114, 78, 96, 179, 249, 230, 0, 103, 56, 239, 229, 155, 123, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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