Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0525d57a71c8f13677998739bf4155560cebca41ced10bb4dc0bafb01599e25c

Tx prefix hash: 4f5a6222340e516d0594418d818b5671d12a3be183c074bd09c939c90d496415
Tx public key: 069fb468a1b9ab27ea0b151171e49d7f04de86f70d08a0e702e45aee8e9ac7c0
Timestamp: 1710227757 Timestamp [UCT]: 2024-03-12 07:15:57 Age [y:d:h:m:s]: 01:016:05:24:42
Block: 976552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272575 RingCT/type: yes/0
Extra: 01069fb468a1b9ab27ea0b151171e49d7f04de86f70d08a0e702e45aee8e9ac7c00211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f63686ceaabbb57404cda5ee758eeeccd817dd4c36af067d15dcf5ac40a421c9 0.600000000000 1436547 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": 976562, "vin": [ { "gen": { "height": 976552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f63686ceaabbb57404cda5ee758eeeccd817dd4c36af067d15dcf5ac40a421c9" } } ], "extra": [ 1, 6, 159, 180, 104, 161, 185, 171, 39, 234, 11, 21, 17, 113, 228, 157, 127, 4, 222, 134, 247, 13, 8, 160, 231, 2, 228, 90, 238, 142, 154, 199, 192, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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