Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06d9d01636754738c0cdda8d89d293659c579b530e1735b0021568f87440736d

Tx prefix hash: 0c764b019c7e2c597aa6272623b220f2b26151f5e8bf56a7f9a91a5f5dced9a9
Tx public key: 39a074dff775387534e277d83799b3841330c41d434d2aaeaf08efc6efaf177d
Timestamp: 1706111225 Timestamp [UCT]: 2024-01-24 15:47:05 Age [y:d:h:m:s]: 01:147:14:26:30
Block: 942381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366497 RingCT/type: yes/0
Extra: 0139a074dff775387534e277d83799b3841330c41d434d2aaeaf08efc6efaf177d0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7906c8e2b2e03246c9dce3f799f04c625b0c8ad67e33c7903cfc90efa27a388b 0.600000000000 1400551 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": 942391, "vin": [ { "gen": { "height": 942381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7906c8e2b2e03246c9dce3f799f04c625b0c8ad67e33c7903cfc90efa27a388b" } } ], "extra": [ 1, 57, 160, 116, 223, 247, 117, 56, 117, 52, 226, 119, 216, 55, 153, 179, 132, 19, 48, 196, 29, 67, 77, 42, 174, 175, 8, 239, 198, 239, 175, 23, 125, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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