Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1bb753d25dc72f0d55672430c1f08b67224ccb8e6dd099a4e77ed6d9c75b488

Tx prefix hash: 4274f7ff30741b309d36d9c89918e1f70b77d4bba81137c33f3d02dffce5b2b5
Tx public key: 1e2cab136342b3b2f9fa17230c1a0e0913505b21c028cab16a872f4683876126
Timestamp: 1762021272 Timestamp [UCT]: 2025-11-01 18:21:12 Age [y:d:h:m:s]: 00:009:06:52:15
Block: 1402816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6636 RingCT/type: yes/0
Extra: 011e2cab136342b3b2f9fa17230c1a0e0913505b21c028cab16a872f4683876126021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b93b0dccc17398345c720602dc2d8efbc4b72fad6697edce8c35d7b16259481 0.600000000000 1891139 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": 1402826, "vin": [ { "gen": { "height": 1402816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b93b0dccc17398345c720602dc2d8efbc4b72fad6697edce8c35d7b16259481" } } ], "extra": [ 1, 30, 44, 171, 19, 99, 66, 179, 178, 249, 250, 23, 35, 12, 26, 14, 9, 19, 80, 91, 33, 192, 40, 202, 177, 106, 135, 47, 70, 131, 135, 97, 38, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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