Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ecb578f0a30012c4086a27abd649c715a9e013e5d971be8cb72be079dc60cfc

Tx prefix hash: 2063f58801beb30d8fac1f094ef29e20c4f1638ea3c52f0b92c870727286bf31
Tx public key: 592a91496f322993fc11d31462624438d4ead324f88aa94d3349b396532a20b6
Timestamp: 1751034506 Timestamp [UCT]: 2025-06-27 14:28:26 Age [y:d:h:m:s]: 00:144:21:02:35
Block: 1313903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101585 RingCT/type: yes/0
Extra: 01592a91496f322993fc11d31462624438d4ead324f88aa94d3349b396532a20b6021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7410a53d85eaa7fca034b2f46a3b1af694770f4da2382ab9a1656089b3997a6f 0.600000000000 1801546 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": 1313913, "vin": [ { "gen": { "height": 1313903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7410a53d85eaa7fca034b2f46a3b1af694770f4da2382ab9a1656089b3997a6f" } } ], "extra": [ 1, 89, 42, 145, 73, 111, 50, 41, 147, 252, 17, 211, 20, 98, 98, 68, 56, 212, 234, 211, 36, 248, 138, 169, 77, 51, 73, 179, 150, 83, 42, 32, 182, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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