Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b435387578550a1ebc455e1269ff765d1bde9910e0c88a036fb98d74b327d5e3

Tx prefix hash: 6aef516ad95bbc841a44f0292143be046c112f32191a08742c459cbf7a6d3cb9
Tx public key: 95a9612db2ea6adca4430e207a7b3942593642f4be09821822e8c852d341453f
Timestamp: 1696597252 Timestamp [UCT]: 2023-10-06 13:00:52 Age [y:d:h:m:s]: 01:097:18:42:55
Block: 863738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331144 RingCT/type: yes/0
Extra: 0195a9612db2ea6adca4430e207a7b3942593642f4be09821822e8c852d341453f02110000000afaf35c9c000000000000000000

1 output(s) for total of 0.843485241000 dcy

stealth address amount amount idx
00: 54561e2aff69c62ceb069a4bdf0c1e41446016ddc3de9f4906dfe028c95b7ed2 0.843485241000 1318214 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": 863748, "vin": [ { "gen": { "height": 863738 } } ], "vout": [ { "amount": 843485241, "target": { "key": "54561e2aff69c62ceb069a4bdf0c1e41446016ddc3de9f4906dfe028c95b7ed2" } } ], "extra": [ 1, 149, 169, 97, 45, 178, 234, 106, 220, 164, 67, 14, 32, 122, 123, 57, 66, 89, 54, 66, 244, 190, 9, 130, 24, 34, 232, 200, 82, 211, 65, 69, 63, 2, 17, 0, 0, 0, 10, 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