Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d077c633df8256fdc7299290f41f6502310c39f0e5aa6f64ecda212cc8ff0145

Tx prefix hash: 93a8a91f39b156432de2762522b7381a52e8bca061314d1f76729eeedc7178f6
Tx public key: 71cee1e832a22c302a2bedf4042f1d31f38039ddbe82bacc6cde472efb121e65
Timestamp: 1701226271 Timestamp [UCT]: 2023-11-29 02:51:11 Age [y:d:h:m:s]: 01:149:03:36:50
Block: 901906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367774 RingCT/type: yes/0
Extra: 0171cee1e832a22c302a2bedf4042f1d31f38039ddbe82bacc6cde472efb121e650211000000074b8f5122000000000000000000

1 output(s) for total of 0.630392451000 dcy

stealth address amount amount idx
00: a6839dd45196b86b0c1d527c79b97d9aa94406fec4288015ae9afc2bebf856d9 0.630392451000 1358501 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": 901916, "vin": [ { "gen": { "height": 901906 } } ], "vout": [ { "amount": 630392451, "target": { "key": "a6839dd45196b86b0c1d527c79b97d9aa94406fec4288015ae9afc2bebf856d9" } } ], "extra": [ 1, 113, 206, 225, 232, 50, 162, 44, 48, 42, 43, 237, 244, 4, 47, 29, 49, 243, 128, 57, 221, 190, 130, 186, 204, 108, 222, 71, 46, 251, 18, 30, 101, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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