Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd45aa328ed403c891015f50d110e6126da95ed9135097c85c3962fb3afc9da3

Tx prefix hash: cecb71cfcf8d1f11b90f38c38aa8af460c42be15e94ba995035940866f2060e9
Tx public key: bfee648448c8190240b7d57202ba64c6a9870b769dcb4d0f69f291fa3bb142e2
Timestamp: 1577797359 Timestamp [UCT]: 2019-12-31 13:02:39 Age [y:d:h:m:s]: 05:064:15:43:34
Block: 35751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195964 RingCT/type: yes/0
Extra: 01bfee648448c8190240b7d57202ba64c6a9870b769dcb4d0f69f291fa3bb142e202110000000e8a2ee0d9000000000000000000

1 output(s) for total of 467.251227286000 dcy

stealth address amount amount idx
00: 7209576111cc5f0d18034b07ba55666f5ddd3fcdedab9504a639eeda74145dc1 467.251227286000 60369 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": 35761, "vin": [ { "gen": { "height": 35751 } } ], "vout": [ { "amount": 467251227286, "target": { "key": "7209576111cc5f0d18034b07ba55666f5ddd3fcdedab9504a639eeda74145dc1" } } ], "extra": [ 1, 191, 238, 100, 132, 72, 200, 25, 2, 64, 183, 213, 114, 2, 186, 100, 198, 169, 135, 11, 118, 157, 203, 77, 15, 105, 242, 145, 250, 59, 177, 66, 226, 2, 17, 0, 0, 0, 14, 138, 46, 224, 217, 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