Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 609d9f709afb963e398060e7cced94d61672ca8d3cb8c300714a1c56672608d1

Tx prefix hash: 7ba89c93274a083afbbe4e9f64d395dcf1fa570bbe22374559f0ae72473f23c3
Tx public key: 8f2662d40c8b2fa23b3616ce05fd5c9a2dd7794e3277642e045f389765a66c1c
Timestamp: 1688379705 Timestamp [UCT]: 2023-07-03 10:21:45 Age [y:d:h:m:s]: 01:323:06:51:23
Block: 795666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492234 RingCT/type: yes/0
Extra: 018f2662d40c8b2fa23b3616ce05fd5c9a2dd7794e3277642e045f389765a66c1c02110000000433af99f4000000000000000000

1 output(s) for total of 1.417843778000 dcy

stealth address amount amount idx
00: b496e87db5a57b7ab66f426e8ed29a7d550eb2c2cc5e594d3520223925781b32 1.417843778000 1246489 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": 795676, "vin": [ { "gen": { "height": 795666 } } ], "vout": [ { "amount": 1417843778, "target": { "key": "b496e87db5a57b7ab66f426e8ed29a7d550eb2c2cc5e594d3520223925781b32" } } ], "extra": [ 1, 143, 38, 98, 212, 12, 139, 47, 162, 59, 54, 22, 206, 5, 253, 92, 154, 45, 215, 121, 78, 50, 119, 100, 46, 4, 95, 56, 151, 101, 166, 108, 28, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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