Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e845ed1a8f473b2efb0ea1bb2f694775790ee6425b603e46cd42270bc39a4a99

Tx prefix hash: 2f35fe1478acb4815912cde54ad5d77cc0ce9154b07422d16eb7489f272930f8
Tx public key: 0bbf89e0e131ee828ce443418f6bd6dd174d4f2fbab3504d0782b1bcdc8d163b
Timestamp: 1714204703 Timestamp [UCT]: 2024-04-27 07:58:23 Age [y:d:h:m:s]: 01:010:02:31:21
Block: 1009506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268163 RingCT/type: yes/0
Extra: 010bbf89e0e131ee828ce443418f6bd6dd174d4f2fbab3504d0782b1bcdc8d163b02110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d11da1c4bda5d03fc04d9cc97fd6316c2fbac2d5a1da6c2ef99efceeeddf48b7 0.600000000000 1471198 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": 1009516, "vin": [ { "gen": { "height": 1009506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d11da1c4bda5d03fc04d9cc97fd6316c2fbac2d5a1da6c2ef99efceeeddf48b7" } } ], "extra": [ 1, 11, 191, 137, 224, 225, 49, 238, 130, 140, 228, 67, 65, 143, 107, 214, 221, 23, 77, 79, 47, 186, 179, 80, 77, 7, 130, 177, 188, 220, 141, 22, 59, 2, 17, 0, 0, 0, 14, 89, 218, 211, 245, 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