Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c18c4cdcd327bd88a199a8c2641d7fb3e8509a77895a7d2f4a078cd9af3f3f2

Tx prefix hash: 417bdefc952327a4f07dce5f8d90c5a6c7e42a933ea31df9d8127ee0b3e6b0eb
Tx public key: 255d96e330e68ba1d64551330942fb12b6a71fa2d0f55d7ba5eec1731151cab9
Timestamp: 1696120681 Timestamp [UCT]: 2023-10-01 00:38:01 Age [y:d:h:m:s]: 01:149:04:55:52
Block: 859786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367655 RingCT/type: yes/0
Extra: 01255d96e330e68ba1d64551330942fb12b6a71fa2d0f55d7ba5eec1731151cab90211000000094b8f5122000000000000000000

1 output(s) for total of 0.869304865000 dcy

stealth address amount amount idx
00: 772c77ce352095a200d57d42012509800f7aacd9d18450aa2664feb836a02dc1 0.869304865000 1314032 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": 859796, "vin": [ { "gen": { "height": 859786 } } ], "vout": [ { "amount": 869304865, "target": { "key": "772c77ce352095a200d57d42012509800f7aacd9d18450aa2664feb836a02dc1" } } ], "extra": [ 1, 37, 93, 150, 227, 48, 230, 139, 161, 214, 69, 81, 51, 9, 66, 251, 18, 182, 167, 31, 162, 208, 245, 93, 123, 165, 238, 193, 115, 17, 81, 202, 185, 2, 17, 0, 0, 0, 9, 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