Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0e7eea9f5b968c65d4c0e77f3c2302f7749157a4ff478505e795afe3072297f

Tx prefix hash: 52fc906d9041e98019a4fe6f134530ce96f61234d5a38d5f16ae46bc7360e7e2
Tx public key: f25333ba3ef042d7aeb33eff0bb8d3b84a08e5b6671814a210e406b93074c462
Timestamp: 1694878488 Timestamp [UCT]: 2023-09-16 15:34:48 Age [y:d:h:m:s]: 01:252:01:29:30
Block: 849470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441287 RingCT/type: yes/0
Extra: 01f25333ba3ef042d7aeb33eff0bb8d3b84a08e5b6671814a210e406b93074c462021100000003faf35c9c000000000000000000

1 output(s) for total of 0.940488123000 dcy

stealth address amount amount idx
00: 58c7636969c648fd2da0524d3015db63830df50a70657115d63ce469373d7c3c 0.940488123000 1303136 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": 849480, "vin": [ { "gen": { "height": 849470 } } ], "vout": [ { "amount": 940488123, "target": { "key": "58c7636969c648fd2da0524d3015db63830df50a70657115d63ce469373d7c3c" } } ], "extra": [ 1, 242, 83, 51, 186, 62, 240, 66, 215, 174, 179, 62, 255, 11, 184, 211, 184, 74, 8, 229, 182, 103, 24, 20, 162, 16, 228, 6, 185, 48, 116, 196, 98, 2, 17, 0, 0, 0, 3, 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