Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 813438ff75823a529f6040e3e8ecb4041dff3acc8518c7afdc4c7e7e464f36cd

Tx prefix hash: dcd3f0080f01e3f9f6127db66e570dd0093eae017709104e54b4dbe5cec335f2
Tx public key: 8d508024ddc2023ceb4ba9dfa6ccef6f060c4e32ab9dca69fc50205bac27a81e
Timestamp: 1720845119 Timestamp [UCT]: 2024-07-13 04:31:59 Age [y:d:h:m:s]: 00:278:14:08:28
Block: 1064577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199016 RingCT/type: yes/0
Extra: 018d508024ddc2023ceb4ba9dfa6ccef6f060c4e32ab9dca69fc50205bac27a81e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37b0b60f34a1cf395cd5c50c0a31d10cfdd77fb3fafe2bde431595bc91cd355e 0.600000000000 1535106 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": 1064587, "vin": [ { "gen": { "height": 1064577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37b0b60f34a1cf395cd5c50c0a31d10cfdd77fb3fafe2bde431595bc91cd355e" } } ], "extra": [ 1, 141, 80, 128, 36, 221, 194, 2, 60, 235, 75, 169, 223, 166, 204, 239, 111, 6, 12, 78, 50, 171, 157, 202, 105, 252, 80, 32, 91, 172, 39, 168, 30, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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