Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a48878b3824981782652b56cb8874855794bd8c75179dfbef0dbd15b8ea77e

Tx prefix hash: 6e0b7124e6bfca4c06323fc2cf515f9495a0a790dfc5c743f6d0d16df1bb2da9
Tx public key: 4974971bf5a6f42b6ec483d3a0ee505c70857abd49d445ae281adaa200d1be59
Timestamp: 1733267689 Timestamp [UCT]: 2024-12-03 23:14:49 Age [y:d:h:m:s]: 00:112:11:42:14
Block: 1167454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80167 RingCT/type: yes/0
Extra: 014974971bf5a6f42b6ec483d3a0ee505c70857abd49d445ae281adaa200d1be590211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b588e62f288f431d082d423c049990300bad7dd9d1364e734a447ea696d66d5a 0.600000000000 1653151 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": 1167464, "vin": [ { "gen": { "height": 1167454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b588e62f288f431d082d423c049990300bad7dd9d1364e734a447ea696d66d5a" } } ], "extra": [ 1, 73, 116, 151, 27, 245, 166, 244, 43, 110, 196, 131, 211, 160, 238, 80, 92, 112, 133, 122, 189, 73, 212, 69, 174, 40, 26, 218, 162, 0, 209, 190, 89, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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