Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 963454a00c224128fe3e34d25c6fc2ef0a5121c9faecb91b86b0bd8129953921

Tx prefix hash: 27940310d99e3360cdb29a4f2ceb1886a654ef6f6c5f36d555bab34d98e507b0
Tx public key: bb1ab43d260efcd47f7c0fa38ed6f9f6e499e6843bcef39a10c13f2aacb2f94e
Timestamp: 1700308991 Timestamp [UCT]: 2023-11-18 12:03:11 Age [y:d:h:m:s]: 01:358:20:07:40
Block: 894301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515364 RingCT/type: yes/0
Extra: 01bb1ab43d260efcd47f7c0fa38ed6f9f6e499e6843bcef39a10c13f2aacb2f94e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.668050874000 dcy

stealth address amount amount idx
00: ca54b9e860b9c02c0c04c058b7b59ba3549cbe103d12372a073b57c1d5e3b3c4 0.668050874000 1350496 of 0

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": 894311, "vin": [ { "gen": { "height": 894301 } } ], "vout": [ { "amount": 668050874, "target": { "key": "ca54b9e860b9c02c0c04c058b7b59ba3549cbe103d12372a073b57c1d5e3b3c4" } } ], "extra": [ 1, 187, 26, 180, 61, 38, 14, 252, 212, 127, 124, 15, 163, 142, 214, 249, 246, 228, 153, 230, 132, 59, 206, 243, 154, 16, 193, 63, 42, 172, 178, 249, 78, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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