Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547fceaf873eacacaa909e1d42424e9f3751f3164d6d42ab013ffde2b37b819a

Tx prefix hash: f05e3f7e24b7216e5769ad1e9b34b4cccfed4a132794f9111a166c381af0e2d0
Tx public key: 1fc4363ac3d35454292f643ef8030c78a2ad29332fc640d34c4c272f86cb92b0
Timestamp: 1749732724 Timestamp [UCT]: 2025-06-12 12:52:04 Age [y:d:h:m:s]: 00:151:08:42:18
Block: 1303466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105885 RingCT/type: yes/0
Extra: 011fc4363ac3d35454292f643ef8030c78a2ad29332fc640d34c4c272f86cb92b0021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f433fafa24b7f489b85c4352d0774c15be6860a9ea55ba1b8e53cdee8eacdce 0.600000000000 1791047 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": 1303476, "vin": [ { "gen": { "height": 1303466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f433fafa24b7f489b85c4352d0774c15be6860a9ea55ba1b8e53cdee8eacdce" } } ], "extra": [ 1, 31, 196, 54, 58, 195, 211, 84, 84, 41, 47, 100, 62, 248, 3, 12, 120, 162, 173, 41, 51, 47, 198, 64, 211, 76, 76, 39, 47, 134, 203, 146, 176, 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