Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60b19febcf0aac07194924bb66da74e5c51e8a9f2f2c827ea9fdfc2d21c25673

Tx prefix hash: 247a89c490fab8a9381069869c5d5c627579d07d66c91334d115887893f852dc
Tx public key: d90f9c501f99fc75ba4f14b99ead5ffbea4bb8370bebf4941c9d096845b0648a
Timestamp: 1744685264 Timestamp [UCT]: 2025-04-15 02:47:44 Age [y:d:h:m:s]: 00:252:20:45:26
Block: 1261701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178483 RingCT/type: yes/0
Extra: 01d90f9c501f99fc75ba4f14b99ead5ffbea4bb8370bebf4941c9d096845b0648a0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef4849be749a01b2f9ed5c88dfa1b30cac051457db4f56fb5ea92a467afcdc34 0.600000000000 1748874 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": 1261711, "vin": [ { "gen": { "height": 1261701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef4849be749a01b2f9ed5c88dfa1b30cac051457db4f56fb5ea92a467afcdc34" } } ], "extra": [ 1, 217, 15, 156, 80, 31, 153, 252, 117, 186, 79, 20, 185, 158, 173, 95, 251, 234, 75, 184, 55, 11, 235, 244, 148, 28, 157, 9, 104, 69, 176, 100, 138, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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