Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a4339b5445e5106deaba0e0711382471fca87327db70c13c2ba60b59776fa25

Tx prefix hash: 24516cdda9044f144013a0960df7d06976e1c5d29656d2ebfc9832d652e5e945
Tx public key: bc17f2c5f0542f175bea6a9e2efc176453257dd59c310cf55b4e5861bfb7b66f
Timestamp: 1702331097 Timestamp [UCT]: 2023-12-11 21:44:57 Age [y:d:h:m:s]: 00:339:11:13:58
Block: 911081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243060 RingCT/type: yes/0
Extra: 01bc17f2c5f0542f175bea6a9e2efc176453257dd59c310cf55b4e5861bfb7b66f02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a0a85ead4a6cf827261df4d4ddcf8474a10fd8e68cbba12c1a17b5509f6ddf7 0.600000000000 1368256 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": 911091, "vin": [ { "gen": { "height": 911081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a0a85ead4a6cf827261df4d4ddcf8474a10fd8e68cbba12c1a17b5509f6ddf7" } } ], "extra": [ 1, 188, 23, 242, 197, 240, 84, 47, 23, 91, 234, 106, 158, 46, 252, 23, 100, 83, 37, 125, 213, 156, 49, 12, 245, 91, 78, 88, 97, 191, 183, 182, 111, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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