Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10dfd9c2d00554f97e9c8b287dcb689cde3a32b9169383f2e4edfd9e98b0c49c

Tx prefix hash: 86a0c542f51fa47dbe4604f3339b66c012e4d8c53c5ccfe5a69e1735590c044f
Tx public key: 573202d7bc6fbe1e49b9aad050da9e36d6c25cae6f78fe25cf73852b0db4e9e5
Timestamp: 1711132510 Timestamp [UCT]: 2024-03-22 18:35:10 Age [y:d:h:m:s]: 01:089:09:22:10
Block: 984061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324749 RingCT/type: yes/0
Extra: 01573202d7bc6fbe1e49b9aad050da9e36d6c25cae6f78fe25cf73852b0db4e9e502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d371b257c4e0b3d277f7a9541c559664df3a52d59e20dc8faafc3a76e2bd0df0 0.600000000000 1444216 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": 984071, "vin": [ { "gen": { "height": 984061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d371b257c4e0b3d277f7a9541c559664df3a52d59e20dc8faafc3a76e2bd0df0" } } ], "extra": [ 1, 87, 50, 2, 215, 188, 111, 190, 30, 73, 185, 170, 208, 80, 218, 158, 54, 214, 194, 92, 174, 111, 120, 254, 37, 207, 115, 133, 43, 13, 180, 233, 229, 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