Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a67d7ddb4fe7b14236488b2a7b3e0916091e12211a291b894bfaf7138efc4bd

Tx prefix hash: 7d395a16507207334247b0f9eaea8ac68b449d686fa031d3272d3db5873ec243
Tx public key: 288b3ba7729f64e27ace4ef8e4a7695227d972cb9fcbece341d696dbc6a8cab7
Timestamp: 1722235446 Timestamp [UCT]: 2024-07-29 06:44:06 Age [y:d:h:m:s]: 00:243:07:09:24
Block: 1076094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173779 RingCT/type: yes/0
Extra: 01288b3ba7729f64e27ace4ef8e4a7695227d972cb9fcbece341d696dbc6a8cab70211000000018c7e50ca000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8a7c143d305f16c57ede8bf489a0bbe24222bc33585e4187ac6e81c6d905ee2 0.600000000000 1548629 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": 1076104, "vin": [ { "gen": { "height": 1076094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8a7c143d305f16c57ede8bf489a0bbe24222bc33585e4187ac6e81c6d905ee2" } } ], "extra": [ 1, 40, 139, 59, 167, 114, 159, 100, 226, 122, 206, 78, 248, 228, 167, 105, 82, 39, 217, 114, 203, 159, 203, 236, 227, 65, 214, 150, 219, 198, 168, 202, 183, 2, 17, 0, 0, 0, 1, 140, 126, 80, 202, 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