Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f45c91b5e3f21df856b81db2cd2d05f07f488719ff74963ddd9a0184fb181e1a

Tx prefix hash: a9e755e50bf9d6b11773c528bde03e32b8bc4ec5d6937d6dde33c9601ff73e40
Tx public key: 22a15e2aca028b6d3a47eb0f74c2e964b54f6159b0c0fe4182b2feabddd663f9
Timestamp: 1719014159 Timestamp [UCT]: 2024-06-21 23:55:59 Age [y:d:h:m:s]: 00:294:19:10:50
Block: 1049364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210679 RingCT/type: yes/0
Extra: 0122a15e2aca028b6d3a47eb0f74c2e964b54f6159b0c0fe4182b2feabddd663f902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5a1d91f967a14ff58b2c77e16411974cb038dc7be68ec395b56b39a5b3b665e 0.600000000000 1519463 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": 1049374, "vin": [ { "gen": { "height": 1049364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5a1d91f967a14ff58b2c77e16411974cb038dc7be68ec395b56b39a5b3b665e" } } ], "extra": [ 1, 34, 161, 94, 42, 202, 2, 139, 109, 58, 71, 235, 15, 116, 194, 233, 100, 181, 79, 97, 89, 176, 192, 254, 65, 130, 178, 254, 171, 221, 214, 99, 249, 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