Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd34e272a9cccb584f4f2f319e6323a3cb4b8260d3e4a00c6dafc503510fd2c

Tx prefix hash: 1620c7f009eef96d4b7ce399d8106526428d57e63953301a25d784ab47c260b4
Tx public key: b0463b846e53aa99ead164568dc250888241a8e26a0a0ba049e371bbaa7263bb
Timestamp: 1755328446 Timestamp [UCT]: 2025-08-16 07:14:06 Age [y:d:h:m:s]: 00:164:14:04:35
Block: 1347690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117326 RingCT/type: yes/0
Extra: 01b0463b846e53aa99ead164568dc250888241a8e26a0a0ba049e371bbaa7263bb021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77a5fda7212bb39c14219b3042f7f32e210e4b91dbd4000edf01c3c29bf9e0ba 0.600000000000 1835611 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": 1347700, "vin": [ { "gen": { "height": 1347690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77a5fda7212bb39c14219b3042f7f32e210e4b91dbd4000edf01c3c29bf9e0ba" } } ], "extra": [ 1, 176, 70, 59, 132, 110, 83, 170, 153, 234, 209, 100, 86, 141, 194, 80, 136, 130, 65, 168, 226, 106, 10, 11, 160, 73, 227, 113, 187, 170, 114, 99, 187, 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