Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bbd5136c2ad89f35830cd80985d5173de203ad627951ad1dc638ee25e8b695f

Tx prefix hash: bf5fba55de814f4ee5e102249229ff16bfc66c2bc3d131c1170342c9566c9fd5
Tx public key: 7988eddc6b652c1804fbe111ae6ab4506e7a37ec2f9fdce3f3dc6b93c15dd4ea
Timestamp: 1713929742 Timestamp [UCT]: 2024-04-24 03:35:42 Age [y:d:h:m:s]: 00:214:16:15:01
Block: 1007233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153677 RingCT/type: yes/0
Extra: 017988eddc6b652c1804fbe111ae6ab4506e7a37ec2f9fdce3f3dc6b93c15dd4ea0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 760e3054c5aad748c6575b88733d8ff3d982166679d6ba9ade570fa81752de9a 0.600000000000 1468507 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": 1007243, "vin": [ { "gen": { "height": 1007233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "760e3054c5aad748c6575b88733d8ff3d982166679d6ba9ade570fa81752de9a" } } ], "extra": [ 1, 121, 136, 237, 220, 107, 101, 44, 24, 4, 251, 225, 17, 174, 106, 180, 80, 110, 122, 55, 236, 47, 159, 220, 227, 243, 220, 107, 147, 193, 93, 212, 234, 2, 17, 0, 0, 0, 6, 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