Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 969bc5a2280fd31151fda11757b749a3786494f4ddb5da84059f7515cf4d7440

Tx prefix hash: 5f36187fc71b33e387d03a948d8d0d0281c95bf16bb9fdd9502d506a8eb67c4c
Tx public key: b5007e3cc60ecc370fa8c40c9cb80d2794070a5c90712d51b48c24641f241411
Timestamp: 1714389230 Timestamp [UCT]: 2024-04-29 11:13:50 Age [y:d:h:m:s]: 00:303:20:06:41
Block: 1011035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217166 RingCT/type: yes/0
Extra: 01b5007e3cc60ecc370fa8c40c9cb80d2794070a5c90712d51b48c24641f24141102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f13d6df8fb12384e0d048c2e3e207d32f1a3f0ada213ccdc68cf3663de514a5 0.600000000000 1473157 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": 1011045, "vin": [ { "gen": { "height": 1011035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f13d6df8fb12384e0d048c2e3e207d32f1a3f0ada213ccdc68cf3663de514a5" } } ], "extra": [ 1, 181, 0, 126, 60, 198, 14, 204, 55, 15, 168, 196, 12, 156, 184, 13, 39, 148, 7, 10, 92, 144, 113, 45, 81, 180, 140, 36, 100, 31, 36, 20, 17, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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