Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f392706067e71d52901df09937beb286f270f8bcc3ead45916183ed1efb7f20

Tx prefix hash: 42f5d1b02020c5d3214fcd24e374db5df02c747a5d42a619595138b4c644eaac
Tx public key: e81158e65730e90ed7da709763b13d8efaf6a4097b8fc90416c1b9d54c80390d
Timestamp: 1753853719 Timestamp [UCT]: 2025-07-30 05:35:19 Age [y:d:h:m:s]: 00:112:08:37:15
Block: 1336442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79129 RingCT/type: yes/0
Extra: 01e81158e65730e90ed7da709763b13d8efaf6a4097b8fc90416c1b9d54c80390d021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f16c2449b2040401906c88b080f2bb0a1fd75e27a3e85d2e3811ddb4664255 0.600000000000 1824243 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": 1336452, "vin": [ { "gen": { "height": 1336442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f16c2449b2040401906c88b080f2bb0a1fd75e27a3e85d2e3811ddb4664255" } } ], "extra": [ 1, 232, 17, 88, 230, 87, 48, 233, 14, 215, 218, 112, 151, 99, 177, 61, 142, 250, 246, 164, 9, 123, 143, 201, 4, 22, 193, 185, 213, 76, 128, 57, 13, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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