Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f654bfc7eb7484e20527630bb73cea6ab272ea88a9a0f615790bc6c4dc772c7

Tx prefix hash: 5ef2d6a3c4fe0f7f2546c39d203ab7fda000b9edc72d147da8b98f83667aea35
Tx public key: 776f573f3e7d7a605d2ef961108058deba0525f29fb5cc6dbabce3d1e9f6f875
Timestamp: 1696699524 Timestamp [UCT]: 2023-10-07 17:25:24 Age [y:d:h:m:s]: 01:108:10:38:06
Block: 864584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338731 RingCT/type: yes/0
Extra: 01776f573f3e7d7a605d2ef961108058deba0525f29fb5cc6dbabce3d1e9f6f87502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.838058504000 dcy

stealth address amount amount idx
00: eca821a3a268c93453390feab909195373a04a9ad441c3f79a9d7b13e194e3d6 0.838058504000 1319104 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": 864594, "vin": [ { "gen": { "height": 864584 } } ], "vout": [ { "amount": 838058504, "target": { "key": "eca821a3a268c93453390feab909195373a04a9ad441c3f79a9d7b13e194e3d6" } } ], "extra": [ 1, 119, 111, 87, 63, 62, 125, 122, 96, 93, 46, 249, 97, 16, 128, 88, 222, 186, 5, 37, 242, 159, 181, 204, 109, 186, 188, 227, 209, 233, 246, 248, 117, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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