Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94c3b5ef8b76554ce64793d0c9bea00a7dd7de9a15366af1c7bcdc267ad7505c

Tx prefix hash: cca4827b19a2d0e20cbd88e998e3013a7189b4ef6a297341727525f8a9501300
Tx public key: f512ada9fd299db2d115e0b40e659e22518da0882d11e9e42442c9a8ab2fb7e6
Timestamp: 1695539633 Timestamp [UCT]: 2023-09-24 07:13:53 Age [y:d:h:m:s]: 01:095:08:07:35
Block: 854967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329408 RingCT/type: yes/0
Extra: 01f512ada9fd299db2d115e0b40e659e22518da0882d11e9e42442c9a8ab2fb7e6021100000004faf35c9c000000000000000000

1 output(s) for total of 0.901860705000 dcy

stealth address amount amount idx
00: 85cc39d2a5056d57324352d8957c619edd2eb546208c9440963ac0c4055622bc 0.901860705000 1308961 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": 854977, "vin": [ { "gen": { "height": 854967 } } ], "vout": [ { "amount": 901860705, "target": { "key": "85cc39d2a5056d57324352d8957c619edd2eb546208c9440963ac0c4055622bc" } } ], "extra": [ 1, 245, 18, 173, 169, 253, 41, 157, 178, 209, 21, 224, 180, 14, 101, 158, 34, 81, 141, 160, 136, 45, 17, 233, 228, 36, 66, 201, 168, 171, 47, 183, 230, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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