Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a13acacc3269e54edd561e6f47bcf5016bf3bfd6bdfd507f3893477b9463cae7

Tx prefix hash: d4cefdbdd0abea38435e0f221b5de07d76b92a8057624b940d369174dc2dc278
Tx public key: d46c4ca3c0e54f379132e8a401f167177676d1ecde9a90a90ad0f21c16ebfeb4
Timestamp: 1758434601 Timestamp [UCT]: 2025-09-21 06:03:21 Age [y:d:h:m:s]: 00:067:05:23:47
Block: 1373088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48136 RingCT/type: yes/0
Extra: 01d46c4ca3c0e54f379132e8a401f167177676d1ecde9a90a90ad0f21c16ebfeb4021100000006b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f5f8b26149d0886fdf04dbdf54d852c5b0061ebfb01e88d26960d98a0a02396 0.600000000000 1861173 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": 1373098, "vin": [ { "gen": { "height": 1373088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f5f8b26149d0886fdf04dbdf54d852c5b0061ebfb01e88d26960d98a0a02396" } } ], "extra": [ 1, 212, 108, 76, 163, 192, 229, 79, 55, 145, 50, 232, 164, 1, 241, 103, 23, 118, 118, 209, 236, 222, 154, 144, 169, 10, 208, 242, 28, 22, 235, 254, 180, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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