Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8dde4c674848fca63b249045dc56c4835c7c13e0a75da0bfa1a0d4035be3da3

Tx prefix hash: ec2386e6cd9acaaa1ac197e612c6482ec1a8e027db98546fb6d359df67ef1713
Tx public key: 35327e5874d9d61824c35fafc48bd8c74fa999d1567810364a9457e8b7f47a2c
Timestamp: 1729061482 Timestamp [UCT]: 2024-10-16 06:51:22 Age [y:d:h:m:s]: 00:190:19:09:36
Block: 1132694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136142 RingCT/type: yes/0
Extra: 0135327e5874d9d61824c35fafc48bd8c74fa999d1567810364a9457e8b7f47a2c0211000000063cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd0540e79c9f28a38b8816fb67f525587ec2d622d40ab35a2a2a184b386979e3 0.600000000000 1615671 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": 1132704, "vin": [ { "gen": { "height": 1132694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd0540e79c9f28a38b8816fb67f525587ec2d622d40ab35a2a2a184b386979e3" } } ], "extra": [ 1, 53, 50, 126, 88, 116, 217, 214, 24, 36, 195, 95, 175, 196, 139, 216, 199, 79, 169, 153, 209, 86, 120, 16, 54, 74, 148, 87, 232, 183, 244, 122, 44, 2, 17, 0, 0, 0, 6, 60, 208, 252, 6, 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