Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b940869e8e374342481b8bf659df854ad25cd420e6f1812dcc6544e7b938ce56

Tx prefix hash: dd4fb3e8b104c845b341a6b200cf636f59d6c2fb0a3b28bc97a123b61525fc9a
Tx public key: ccc5ae6de0d3b9d72b3f28d0e608cf281a1d61ea2a0a019c4cc199345ba32c69
Timestamp: 1677782587 Timestamp [UCT]: 2023-03-02 18:43:07 Age [y:d:h:m:s]: 01:315:23:15:21
Block: 708439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486748 RingCT/type: yes/0
Extra: 01ccc5ae6de0d3b9d72b3f28d0e608cf281a1d61ea2a0a019c4cc199345ba32c690211000000055029cbac000000000000000000

1 output(s) for total of 2.758337520000 dcy

stealth address amount amount idx
00: 29e86573ec2c99098da36d83b277135f6b2d7934ad39af0aa684b6176c85dbd4 2.758337520000 1152332 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": 708449, "vin": [ { "gen": { "height": 708439 } } ], "vout": [ { "amount": 2758337520, "target": { "key": "29e86573ec2c99098da36d83b277135f6b2d7934ad39af0aa684b6176c85dbd4" } } ], "extra": [ 1, 204, 197, 174, 109, 224, 211, 185, 215, 43, 63, 40, 208, 230, 8, 207, 40, 26, 29, 97, 234, 42, 10, 1, 156, 76, 193, 153, 52, 91, 163, 44, 105, 2, 17, 0, 0, 0, 5, 80, 41, 203, 172, 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