Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50029bf66579ab9654a41206fd544bda2e65bfb39b1558b68a5544ca143658fb

Tx prefix hash: 14f0f57a25b4d9c2f79ec4c3fa449822964cfe4ba8fcf7a59fa0f4cdfba8a926
Tx public key: bf7ee1a06ab31af2a8a7dfe7423d3a96e8b5275ef36573b52b1a927a1952f0f8
Timestamp: 1761866835 Timestamp [UCT]: 2025-10-30 23:27:15 Age [y:d:h:m:s]: 00:006:02:22:46
Block: 1401547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4334 RingCT/type: yes/0
Extra: 01bf7ee1a06ab31af2a8a7dfe7423d3a96e8b5275ef36573b52b1a927a1952f0f8021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a37b5b6943a4f13c6070cd07c13b137fc8ea3017f7f8109cda4d1d3dba003c6a 0.600000000000 1889866 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": 1401557, "vin": [ { "gen": { "height": 1401547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a37b5b6943a4f13c6070cd07c13b137fc8ea3017f7f8109cda4d1d3dba003c6a" } } ], "extra": [ 1, 191, 126, 225, 160, 106, 179, 26, 242, 168, 167, 223, 231, 66, 61, 58, 150, 232, 181, 39, 94, 243, 101, 115, 181, 43, 26, 146, 122, 25, 82, 240, 248, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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