Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8be718483f55178477945f852fb6e040a5299d98f235bca5f87ac4fa1c98324

Tx prefix hash: 7eea0fec267990b812f0c3fd72c0b4da377f785240a97c6aaa76dfeb60a3f71b
Tx public key: d0bcc69cb6cf2427676675b373e30d3a0e68cbde49065dacda84e3947bc9f339
Timestamp: 1725087752 Timestamp [UCT]: 2024-08-31 07:02:32 Age [y:d:h:m:s]: 00:243:17:26:05
Block: 1099737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174059 RingCT/type: yes/0
Extra: 01d0bcc69cb6cf2427676675b373e30d3a0e68cbde49065dacda84e3947bc9f33902110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96bdd4c34c43e4da6f018b243d34ea137ae43b7bac21dd22b6103139c3c4149e 0.600000000000 1575704 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": 1099747, "vin": [ { "gen": { "height": 1099737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96bdd4c34c43e4da6f018b243d34ea137ae43b7bac21dd22b6103139c3c4149e" } } ], "extra": [ 1, 208, 188, 198, 156, 182, 207, 36, 39, 103, 102, 117, 179, 115, 227, 13, 58, 14, 104, 203, 222, 73, 6, 93, 172, 218, 132, 227, 148, 123, 201, 243, 57, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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