Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 572958cb0eb4d72784a8bff1ec47d16a3e46fb7400f316cd9ce3721378af73d6

Tx prefix hash: 7a0d63f2a9954e7377bfc2126d39dd71a3b462b1c2076760b50f59a106ab4dbd
Tx public key: 37bd0557425e6b453b6ac5e12ea5eccd9b932bd282703f4ae6c127e1e52fdcb5
Timestamp: 1657258439 Timestamp [UCT]: 2022-07-08 05:33:59 Age [y:d:h:m:s]: 02:255:08:35:11
Block: 539106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 703649 RingCT/type: yes/0
Extra: 0137bd0557425e6b453b6ac5e12ea5eccd9b932bd282703f4ae6c127e1e52fdcb5021100000011bf7ee4e7000000000000000000

1 output(s) for total of 10.039640843000 dcy

stealth address amount amount idx
00: 8f110de03782a231fd0a0d3ef2ea5c3200b33d1c8ef63d4a4892567dc2f8dc25 10.039640843000 969177 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": 539116, "vin": [ { "gen": { "height": 539106 } } ], "vout": [ { "amount": 10039640843, "target": { "key": "8f110de03782a231fd0a0d3ef2ea5c3200b33d1c8ef63d4a4892567dc2f8dc25" } } ], "extra": [ 1, 55, 189, 5, 87, 66, 94, 107, 69, 59, 106, 197, 225, 46, 165, 236, 205, 155, 147, 43, 210, 130, 112, 63, 74, 230, 193, 39, 225, 229, 47, 220, 181, 2, 17, 0, 0, 0, 17, 191, 126, 228, 231, 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