Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b609f4a1c9694653e15688bf5766f1a681839e52d110b236c96d2c2d9fcfcfa

Tx prefix hash: ff92b152f7de8790ec83892d6d7ad6231df793b7f198c0c86cbcfbdd25551e85
Tx public key: 546a47e0541800bf0e270ccf1facd6e5b0d249c1934d92f68a7153a0650e9bc6
Timestamp: 1755087574 Timestamp [UCT]: 2025-08-13 12:19:34 Age [y:d:h:m:s]: 00:011:07:38:43
Block: 1346058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7582 RingCT/type: yes/0
Extra: 01546a47e0541800bf0e270ccf1facd6e5b0d249c1934d92f68a7153a0650e9bc6021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6505cb7c86eb5cde788a783c4b60c595ec8a29ac3f73cc84cc2601ace4930f4 0.600000000000 1833955 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": 1346068, "vin": [ { "gen": { "height": 1346058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6505cb7c86eb5cde788a783c4b60c595ec8a29ac3f73cc84cc2601ace4930f4" } } ], "extra": [ 1, 84, 106, 71, 224, 84, 24, 0, 191, 14, 39, 12, 207, 31, 172, 214, 229, 176, 210, 73, 193, 147, 77, 146, 246, 138, 113, 83, 160, 101, 14, 155, 198, 2, 17, 0, 0, 0, 7, 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