Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1c75a18ef40d9e08e06eacb116bfeb59676d3f08060920c785bc9b5a2c0428b

Tx prefix hash: a262c6c933c133fbf8c54aaf3d926971a039fd0fb03ff8eb17bf55f220079183
Tx public key: 6f29b4ed3cf6b1004c71a1a8ea1f150d2a91d4e6f44445a8b544c4eddc35b227
Timestamp: 1749721938 Timestamp [UCT]: 2025-06-12 09:52:18 Age [y:d:h:m:s]: 00:150:00:39:24
Block: 1303375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104928 RingCT/type: yes/0
Extra: 016f29b4ed3cf6b1004c71a1a8ea1f150d2a91d4e6f44445a8b544c4eddc35b227021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff2d25a2324cc312a89d5d8eb62fca768ba2d8c472eb2e644281701ac4cbe321 0.600000000000 1790954 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": 1303385, "vin": [ { "gen": { "height": 1303375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff2d25a2324cc312a89d5d8eb62fca768ba2d8c472eb2e644281701ac4cbe321" } } ], "extra": [ 1, 111, 41, 180, 237, 60, 246, 177, 0, 76, 113, 161, 168, 234, 31, 21, 13, 42, 145, 212, 230, 244, 68, 69, 168, 181, 68, 196, 237, 220, 53, 178, 39, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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