Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d9b132a7e99803b85460c9631cd54d4295b7d0a16168fc9202dc25e2c4baa2e

Tx prefix hash: 1f992431c8e400c0fb22d1a0eaff35955ed4fe359e2c6e26f1e98270981ecf54
Tx public key: 5816b48d7b3707e565a3f7c4ed8ca5153034ed919ad11a43205d194baf8c1139
Timestamp: 1705942116 Timestamp [UCT]: 2024-01-22 16:48:36 Age [y:d:h:m:s]: 01:142:18:09:53
Block: 940970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363136 RingCT/type: yes/0
Extra: 015816b48d7b3707e565a3f7c4ed8ca5153034ed919ad11a43205d194baf8c113902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfa6646554b0994fdaacd501eb607772b3364aaefd4f22e2d6bdc2758349a105 0.600000000000 1399112 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": 940980, "vin": [ { "gen": { "height": 940970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfa6646554b0994fdaacd501eb607772b3364aaefd4f22e2d6bdc2758349a105" } } ], "extra": [ 1, 88, 22, 180, 141, 123, 55, 7, 229, 101, 163, 247, 196, 237, 140, 165, 21, 48, 52, 237, 145, 154, 209, 26, 67, 32, 93, 25, 75, 175, 140, 17, 57, 2, 17, 0, 0, 0, 7, 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